When The Process Changes Without Warning
It is 9:14 on a Tuesday, and Nadia's dashboard is gone.
In its place sits a banner: "Welcome to your new workspace." The shared spreadsheet she has run for two years is somewhere inside this thing. She cannot find any of the color-coded tabs or delivery notes in column H.
Her manager sent one message on Sunday night. The migration was done, and the team should explore the new setup. By 9:40 Nadia has done no work at all.
What actually changed
By lunch she had built a story. The team had been restructured, and nobody told her. Someone had decided her spreadsheet was messy, and asking for help would make her look slow.
None of that happened, though. The company bought a new tool, IT ran the migration on Saturday, and training was booked for Thursday. Nobody told her because nobody thought about her.
When a process changes without warning, your brain fills the silence. It writes a version of events, and you are usually the loser in it. Almost everything you feel in the first two days comes from that gap.
David A. Shore teaches change management at Harvard. He describes the manager's job as "upsetting people only at a rate they can tolerate."
That did not happen here. The silence was a planning failure, and it says nothing about your ability.
TechClass cites a workplace study on exactly this. Employees who were kept well informed during changes were nearly 50 percent more engaged. The changes themselves barely moved engagement.
So the job for the next two weeks is small. Separate what actually changed from what you are imagining. Then work only on the first list.
Ten minutes and two columns
Open a blank page and draw two columns: confirmed and assumed.
- "Confirmed" means you can name where it came from. An email, a message, a person who said it out loud. "The tool changed on Saturday." "Training is Thursday." "My login works."
- Assumed is everything else. "They think I'm slow." "My role is changing." "Everyone else already understands this."
One rule keeps this honest. Something only moves into the confirmed column when you can point at where it came from.
Nadia had four confirmed items and nine assumed ones. Seven of the nine dissolved when she reread Sunday's message properly. The two that survived became questions.
Do not throw the assumed column away. Reread it on Friday. Anything still sitting there after a week is worth raising with someone because it has stopped being noise.
Three questions to ask your manager
Send all three in one message. Do not book a meeting, as it makes the problem feel bigger than it is.
- Which of my tasks change this week, and which stay the same?
- Who do I go to when the tool does something I don't understand?
- Is there a date I need to be fluent by, or am I setting my pace?
The first question gives you scope, so you stop worrying about your whole job. Question two gives you a name, so you stop searching help pages at 11pm. The last one pulls the invisible deadline out of your head.
Send it on a normal working morning, not late at night. The message reads calmer that way, and you get an answer the same day.
If nothing comes back in two days, ask the teammate who replies fastest. Somebody on your team has already found the export button. You are not asking them to teach you the whole tool, only to point at one screen.
Twenty minutes a day, for ten days
Put the block in your calendar at the same time each day. Short daily sessions beat one long class. TechClass builds new-system training as ten-minute tutorials, one a day across a week.
- Days one to three: rebuild something you already know how to do. You know the work. This is only about where the buttons moved.
- Days four to six: find your data. Export one file. Open a test item and break it on purpose.
- Days seven to ten: write your own one-page guide for the three things you do most often. Screenshots and numbered steps, in your own words.
Write the guide for a colleague who joins next month, not for yourself. That forces you to explain the steps instead of hinting at them.
Keep a stuck list beside you the whole time. Every question that stops you mid-task goes on it. Ask the whole list once, on Friday.
Twenty minutes is the version that survives a busy week. If a day gets eaten, take ten and move the rest forward. Skipping the block entirely is what turns two weeks into two months.
What Nadia's Friday looked like
Her guide ran to six steps on one page. She posted it in the team channel that afternoon. Two colleagues used it the same day, and one added a step she had missed.
Her stuck list contained eleven questions, and the training on Thursday addressed seven of them. She asked the other four in the session. She left with the name of the person who owns the report.
She was still slower than she used to be. She had stopped reading that as a verdict on her.
The change was not aimed at you
Jeff Cole is a change consultant who writes for PEX Network. He points out that your new process may be the fourteenth change someone has been asked to absorb that month. Nobody is counting how many have landed on you.
That is what the two columns are for. They are the only place the count gets written down.
Nadia still keeps that page. She pulls it out whenever something moves without warning, and it takes about ten minutes. The confirmed column is always the shorter one.
